Skip to content

[GHSA-h27x-g6w4-24gq] Add missing CVSS 3.1 score from NVD assessment#7386

Closed
PiniShv wants to merge 1 commit intogithub:PiniShv/advisory-improvement-7386from
PiniShv:PiniShv-GHSA-h27x-g6w4-24gq
Closed

[GHSA-h27x-g6w4-24gq] Add missing CVSS 3.1 score from NVD assessment#7386
PiniShv wants to merge 1 commit intogithub:PiniShv/advisory-improvement-7386from
PiniShv:PiniShv-GHSA-h27x-g6w4-24gq

Conversation

@PiniShv
Copy link
Copy Markdown

@PiniShv PiniShv commented Apr 13, 2026

Change

Add the missing CVSS 3.1 score to GHSA-h27x-g6w4-24gq (CVE-2026-27979), the Next.js unbounded resume buffering DoS vulnerability.

What was missing

The advisory currently includes only a CVSS 4.0 vector. NIST independently assessed a CVSS 3.1 score as part of their initial analysis:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H  (7.5 High)

Source: NVD - CVE-2026-27979

Why it matters

The CVSS 4.0 vector rates Availability impact as Low (VA:L), while the NIST CVSS 3.1 assessment rates Availability as High (A:H). For a denial-of-service vulnerability that causes unbounded memory consumption, High availability impact is the more representative assessment. Including the CVSS 3.1 vector gives downstream consumers a more complete picture of the risk.

Many vulnerability scanners, SCA tools, and compliance frameworks still evaluate severity using CVSS 3.1. Without the 3.1 vector in the advisory data, these tools either skip the advisory or produce inaccurate severity mappings.

No other fields were changed.

@github-actions github-actions bot changed the base branch from main to PiniShv/advisory-improvement-7386 April 13, 2026 20:04
@shelbyc
Copy link
Copy Markdown
Contributor

shelbyc commented Apr 14, 2026

Hi @PiniShv, I'm keeping the advisory as it currently is because the CVSS 4.0 score provided by the maintainers in GHSA-h27x-g6w4-24gq is both accurate and adequate. Thank you for your interest in GHSA-h27x-g6w4-24gq.

@shelbyc shelbyc closed this Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants